Network device management technology

ABSTRACT

Techniques are described for providing network device management. In some implementations, a native mobile device application enables use of a mobile device to add new devices to a network, remove devices from a network, change network and device profile settings, troubleshoot a network, provide an interface into network devices, communications, diagnostics, etc., and provide remote access to the network for installation, programming, troubleshooting, and inclusion.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation (and claims the benefit of priorityunder 35 USC 120) of U.S. application Ser. No. 14/703,799, filed May 4,2015, which is a continuation of U.S. application Ser. No. 13/539,767,filed Jul. 2, 2012, now U.S. Pat. No. 9,026,648, issued May 5, 2015,which is a continuation of U.S. application Ser. No. 12/782,674, filedMay 18, 2010, now U.S. Pat. No. 8,214,494, issued Jul. 3, 2012, whichclaims the benefit of U.S. Provisional Application No. 61/179,230, filedMay 18, 2009. These prior applications are incorporated herein byreference in their entirety for all purposes.

TECHNICAL FIELD

This disclosure relates to network device management technology.

BACKGROUND

Many people equip homes and businesses with alarm systems to provideincreased security for their homes and businesses. Alarm systems mayinclude control panels that a person may use to control operation of thealarm system and sensors that monitor for security breaches. In responseto an alarm system detecting a security breach, the alarm system maygenerate an audible alert and, if the alarm system is monitored by amonitoring service, the alarm system may send electronic data to themonitoring service to alert the monitoring service of the securitybreach.

SUMMARY

Techniques are described for network device management.

Implementations of the described techniques may include hardware, amethod or process implemented at least partially in hardware, or acomputer-readable storage medium encoded with executable instructionsthat, when executed by a processor, perform operations.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features will beapparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of an example system.

FIGS. 2, 4, and 6 are flow charts illustrating example processes.

FIG. 3 illustrates an example of a standardized network devicemanagement interface.

FIGS. 5A and 5B illustrate an example of diagnosing a detected problemwith a networked device.

FIG. 7 illustrates an example of updating firmware of networked devices.

DETAILED DESCRIPTION

Techniques are described for providing network device management. Insome implementations, a native mobile device application enables use ofa mobile device to add new devices to a network, remove devices from anetwork, change network and device profile settings, troubleshoot anetwork, provide a GUI interface into network devices, communications,diagnostics, etc., and provide remote access to the network forinstallation, programming, troubleshooting, and inclusion.

FIG. 1 illustrates an example of an electronic system 100 configured toprovide network device management using one or more mobile devices. Theelectronic system 100 includes a network 105, a monitoring systemcontrol unit 110, one or more mobile devices 140, 150, and a monitoringapplication server 160. In some examples, the network 105 facilitatescommunications between the monitoring system control unit 110, the oneor more mobile devices 140, 150, and the monitoring application server160.

The network 105 is configured to enable exchange of electroniccommunications between devices connected to the network 105. Forexample, the network 105 may be configured to enable exchange ofelectronic communications between the monitoring system control unit110, the one or more mobile devices 140, 150, and the monitoringapplication server 160. The network 105 may include, for example, one ormore of the Internet, Wide Area Networks (WANs), Local Area Networks(LANs), analog or digital wired and wireless telephone networks (e.g., apublic switched telephone network (PSTN), Integrated Services DigitalNetwork (ISDN), a cellular network, and Digital Subscriber Line (DSL)),radio, television, cable, satellite, or any other delivery or tunnelingmechanism for carrying data. Network 105 may include multiple networksor subnetworks, each of which may include, for example, a wired orwireless data pathway. The network 105 may include a circuit-switchednetwork, a packet-switched data network, or any other network able tocarry electronic communications (e.g., data or voice communications).For example, the network 105 may include networks based on the Internetprotocol (IP), asynchronous transfer mode (ATM), the PSTN,packet-switched networks based on IP, X.25, or Frame Relay, or othercomparable technologies and may support voice using, for example, VoIP,or other comparable protocols used for voice communications. The network105 may include one or more networks that include wireless data channelsand wireless voice channels. The network 105 may be a wireless network,a broadband network, or a combination of networks including a wirelessnetwork and a broadband network.

The monitoring system control unit 110 includes a controller 112 and anetwork module 114. The controller 112 is configured to control amonitoring system (e.g., a home alarm or security system) that includesthe monitoring system control unit 110. In some examples, the controller112 may include a processor or other control circuitry configured toexecute instructions of a program that controls operation of an alarmsystem. In these examples, the controller 112 may be configured toreceive input from sensors, detectors, or other devices included in thealarm system and control operations of devices included in the alarmsystem or other household devices (e.g., a thermostat, an appliance,lights, etc.). For example, the controller 112 may be configured tocontrol operation of the network module 114 included in the monitoringsystem control unit 110.

The network module 114 is a communication device configured to exchangecommunications over the network 105. The network module 114 may be awireless communication module configured to exchange wirelesscommunications over the network 105. For example, the network module 114may be a wireless communication device configured to exchangecommunications over a wireless data channel and a wireless voicechannel. In this example, the network module 114 may transmit alarm dataover a wireless data channel and establish a two-way voice communicationsession over a wireless voice channel. The wireless communication devicemay include one or more of a GSM module, a radio modem, cellulartransmission module, or any type of module configured to exchangecommunications in one of the following formats: GSM or GPRS, CDMA, EDGEor EGPRS, EV-DO or EVDO, UMTS, or IP.

The network module 114 also may be a wired communication moduleconfigured to exchange communications over the network 105 using a wiredconnection. For instance, the network module 114 may be a modem, anetwork interface card, or another type of network interface device. Thenetwork module 114 may be an Ethernet network card configured to enablethe monitoring system control unit 110 to communicate over a local areanetwork and/or the Internet. The network module 114 also may be avoiceband modem configured to enable the alarm panel to communicate overthe telephone lines of Plain Old Telephone Systems (POTS).

The monitoring system that includes the monitoring system control unit110 includes one or more sensors or detectors. For example, an alarmsystem may include multiple sensors 120 and 122. The sensors 120 and 122may include a contact sensor, a motion sensor, a glass break sensor, orany other type of sensor included in an alarm system or security system.The sensors 120 and 122 also may include an environmental sensor, suchas a temperature sensor, a water sensor, a rain sensor, a wind sensor, alight sensor, a smoke detector, a carbon monoxide detector, an airquality sensor, etc. The sensors 120 and 122 further may include ahealth monitoring sensor, such as a prescription bottle sensor thatmonitors taking of prescriptions, a blood pressure sensor, a blood sugarsensor, a bed mat configured to sense presence of liquid (e.g., bodilyfluids) on the bed mat, etc. In some examples, the sensors 120 and 122may include a radio-frequency identification (RFID) sensor thatidentifies a particular article that includes a pre-assigned RFID tag.In addition, the sensors 120 and 122 may include a video/photographiccamera or other type of optical sensing device configured to captureimages and may include an energy consumption sensor for appliances anddevices in a property monitored by the monitoring system.

The sensors 120 and 122 communicate with the controller 112 overcommunication links 124 and 126. The communication links 124 and 126 maybe a wired or wireless data pathway configured to transmit signals fromthe sensors 120 and 122 to the controller 112. The sensors 120 and 122may continuously transmit sensed values to the controller 112,periodically transmit sensed values to the controller 112, or transmitsensed values to the controller 112 in response to a change in a sensedvalue.

The controller 112 may receive signals from the sensors 120 and 122 anddetect an alarm event based on the sensed values. For example, thesensor 120 may be a contact sensor provided on a door to a residence andthe communication link 124 may be a wireless connection between thesensor 120 and the controller 112. In this example, the sensor 120 maysense that the door has been opened (e.g., absence of a connectionbetween contacts included as part of the sensor) and wirelessly transmitdata over communication link 124 to the controller 112 indicating thatthe door has been opened. The controller 112 receives the data from thesensor 120 over the communication link 124 and determines that an alarmevent (e.g., the door opened) has occurred based on the signal from thesensor 120. The controller 112 controls operation of the alarm systembased on the determination that the alarm event has occurred.

The monitoring system also includes a speaker 130. The speaker 130 mayinclude an electromechanical transducer that converts an electricalsignal into sound. The speaker 130 may receive an electrical signal fromthe controller 112 and produce an audible output based on the electricalsignal. For example, the controller 112, in response to detecting analarm event, may send a signal to the speaker 130 to cause the speakerto produce an audible alarm sound. The speaker 130 also may output audiomessages (e.g., audio advertisements, broadcast audio alerts, etc.). Inanother example, the controller 112 may send a signal representative ofa voice communication to the speaker 130 to cause the speaker to producean audible output of the voice communication.

The monitoring system also includes a display 132. The display 132 maybe any type of electronic display configured to render a visuallyperceivable display of information (e.g., an LCD display, a plasmadisplay, a television, a computer monitor, a digital picture frame, adisplay integrated into an appliance, a display included in a portabledevice of a user, a mirror, a projection display device, etc.). Thedisplay 132 may be integrated in the monitoring system control unit 110(e.g., control panel) or may be separate from the monitoring systemcontrol unit 110 (e.g., a separate display provided as part of thesecurity system or a television, a computer monitor, etc. that is notpart of the security system, but a device with which the security systemmay communicate). The display 132 may be used to depict the currentstate of the monitoring system. For example, an LCD display may displaywords like “System Disarmed 6:42 pm”, or “Enter User Code to Disarm”, or“Front Door Opened”. The display 132 also may be used to displayelectronic content, such as advertisement content, news content, weathercontent, and entertainment content.

The monitoring system control unit 110 communicates with the speaker 130and the display 132 over communication links 134 and 136. Thecommunication links 134 and 136 may be similar to the communicationlinks 124 and 126 described above.

The monitoring application server 160 is an electronic device configuredto provide monitoring services by exchanging electronic communicationswith the monitoring system control unit 110 and the one or more mobiledevices 140, 150 over the network 105. For example, the monitoringapplication server 160 may be configured to monitor events generated bythe monitoring system control unit 110. In this example, the monitoringapplication server 160 may exchange electronic communications with thenetwork module 114 included in the monitoring system control unit 110 toreceive information regarding alarm events detected by the monitoringsystem control unit 110. Additionally or alternatively, the monitoringapplication server 160 may receive information regarding events from theone or more mobile devices 140, 150.

The monitoring application server 160 may store sensor data receivedfrom the monitoring system and perform analysis of sensor data receivedfrom the monitoring system. Based on the analysis, the monitoringapplication server 160 may communicate with and control aspects of themonitoring system control unit 110 or the one or more mobile devices140, 150. The monitoring application server 160 may store networkconfiguration protocols, user guides, and other information that mayassist in configuration of network devices.

The one or more mobile devices 140, 150 are devices that host anddisplay user interfaces and that host one or more native applications(e.g., the native network application 142, 152). The one or more mobiledevices 140, 150 may be cellular phones or non-cellular locallynetworked devices with displays. The one or more mobile devices 140, 150may include a cell phone, a smart phone, a tablet PC, a personal digitalassistant (“PDA”), or any other portable device configured tocommunicate over a network and display information. For example,implementations may also include Blackberry-type devices (e.g., asprovided by Research in Motion), electronic organizers, iPhone-typedevices (e.g., as provided by Apple), iPod devices (e.g., as provided byApple) or other portable music players, other communication devices, andhandheld or portable electronic devices for gaming, communications,and/or data organization. The one or more mobile devices 140, 150 may bethe same or may include mobile devices of different types. The one ormore mobile devices 140, 150 may perform functions unrelated to themonitoring system, such as placing personal telephone calls, playingmusic, playing video, displaying pictures, browsing the Internet,maintaining an electronic calendar, etc.

The one or more mobile devices 140, 150 communicate with and receivemonitoring system data from the monitoring system control unit 110 usingthe communication link 138. For instance, the one or more mobile devices140, 150 may communicate with the monitoring system control unit 110using various local wireless protocols such as wifi, Bluetooth, zwave,zigbee, HomePlug (ethernet over powerline), or wired protocols such asEthernet and USB, to connect the one or more mobile devices 140, 150 tolocal security and automation equipment. The one or more mobile devices140, 150 also may connect locally to other network devices, such as theappliance 170, the printer 172, the camera 174, and the router 176. Thelocal connection may improve the speed of status and controlcommunications because communicating through the network 105 with aremote server (e.g., the monitoring application server 160) may besignificantly slower.

Although the one or more mobile devices 140, 150 are shown as beingconnected to the network 105, in some implementations, the one or moremobile devices 140, 150 are not connected to the network 105. In theseimplementations, the one or more mobile devices 140, 150 communicatedirectly with one or more of the monitoring system components and nonetwork (e.g., Internet) connection or reliance on remote servers isneeded.

The one or more mobile devices 140, 150 each include a native networkapplication 142, 152, respectively. The native network application 142,152 refers to a software/firmware program running on the correspondingmobile device that enables the user interface and features describedbelow. The one or more mobile devices 140, 150 may load or install thenative network application 142, 152 based on data received over anetwork or data received from local media. The native networkapplication 142, 152 runs on mobile devices platforms, such as iPhone,iPod touch, Blackberry, Google Android, Windows Mobile, etc.

The native network application 142, 152 provides an interface forconfiguring and managing devices included in one or more home networks.The native network application 142, 152 functions as a universalprogrammer for multiple, different devices and multiple, differenttechnologies and standards. Many types of home network devices existand, in many cases, interfaces used to control the network devices donot exist, are limited, or are not currently available to a user thatdesires to configure a device on a home network. The native networkapplication 142, 152 may provide users with an easy to use, standardizedinterface with which to configure and manage many different types ofnetwork devices, regardless of whether the network devices use differentprotocols or technologies.

For instance, as shown in FIG. 1, a user's home network may include arefrigerator 170 that communicates with zwave technology, a printer 172that communicates using Bluetooth technology, a camera 174 thatcommunicates using a wireless Internet-based protocol (e.g., 802.11b),and a router 176 that may be configured by accessing web pages madeavailable by the router at a particular IP address. The native networkapplication 142, 152 may provide an interface that enables a user toconfigure all of these different types of devices. The interface may bestandardized between devices such that the user gets the same look andfeel, regardless of which device the user is configuring. This mayassist the user in more easily configuring all devices in the user'shome.

The native network application 142, 152 may be used to add new devicesto a network, remove devices from a network, change network and deviceprofile settings, and troubleshoot a network. The native networkapplication 142, 152 also may provide a GUI interface into networkdevices, communications, diagnostics, etc. and provide remote access toa home network for installation, programming, troubleshooting, andinclusion.

For instance, the native network application 142, 152 may be used as aninclusion device to add and remove zwave nodes on a zwave network (e.g.,add the refrigerator 170). The native network application 142, 152 mayfunction as a zwave controller by using the zwave proprietary protocoland leveraging a zwave communication chip in the mobile device.

In some examples, the native network application 142, 152 may be used asa programming keypad to add/remove/program sensors and other devices onan alarm (intrusion, fire, medical) system. For example, the nativenetwork application 142, 152 may provide an interface to the monitoringsystem control unit 110 to facilitate management of sensors and otherdevices controlled by the monitoring system control unit 110.

The native network application 142, 152 also may be used toadd/remove/program IP video monitoring/surveillance cameras on anIP-based network (e.g., camera 174). The native network application 142,152 may be used as a temporary interface for a networking router, hub,modem or other networked device that does not have its own userinterface or display (e.g., the router 176). For example, the nativenetwork application 142, 152 displays the router settings screenswithout needing to go through a web browser on another network device.

In some implementations, the native network application 142, 152 may beused to program wireless network settings into a router, networkprinter, scanner, etc. This may avoid a user having to go through acomputer web browser or difficult on-device UI.

In implementations in which the mobile device has long-rangecommunication capability (e.g., cellular—GSM, CDMA, LTE etc—WiMax, orother), the native network application 142, 152 may be used to remotelyaccess locally networked devices from anywhere. Any of the devices maybe accessed and all of the applications described above may be performedfrom a remote location.

The native network application 142, 152 also may implement a permissionsystem that provides a different level of control for different users.For instance, parent users may have full control of the network devicesand a child user may have limited control (e.g., the child user may beable to add a first type of device, but may not be able to modifysettings of existing devices or add a second type of device). Thepermission system may be implemented based on user-specific passcodes orparticular mobile devices may be assigned to particular users.

In implementations in which multiple mobile devices are included in thesystem 100, the native network application 142, 152 may include rulesthat govern input from which of the multiple devices controls whenconflicting input is received. For instance, when a parent user isattempting to perform a first action and a child user is attempting toperform a second, different action that conflicts with the first action,the rules of the native network application 142, 152 (or monitoringsystem in general) may perform only the first action because the parentuser has higher priority than the child user.

FIG. 2 illustrates an example process. The operations of the exampleprocess are described generally as being performed by the system 100.The operations of the example process may be performed by one of thecomponents of the system 100 (e.g., the monitoring application server160 or the mobile device 140, 150 with the native network application142, 152) or may be performed by any combination of the components ofthe system 100. In some implementations, operations of the exampleprocesses may be performed by one or more processors included in one ormore electronic devices.

FIG. 2 illustrates an example process 200 for providing a standardizedinterface for managing multiple, different types of networked devices.The system 100 tracks multiple, different types of networked devicesthat are located at a property (210). For instance, the system 100 maymaintain, in electronic storage, a list of networked devices that arelocated at a property. The list of networked devices may include manydifferent types of devices that communicate using many different typesof protocols and perform many different types of functions. The system100 may maintain the list of networked devices based on user inputadding devices to a network located at a property or by tracking devicesautomatically added to the network located at the property. The exampleinterface described in more detail below with respect to FIG. 3illustrates an example list of multiple, different types of networkeddevices that are located at a property and tracked by the system 100.

The system 100 detects status of the multiple, different types ofnetworked devices (220). For example, the system 100 exchangescommunications with the multiple, different types of networked devicesand determines the status of the multiple, different types of networkeddevices. In this example, the system 100 may determine status of themultiple, different types of networked devices by establishing a localconnection with each of the multiple, different types of networkeddevices and receiving status information through the local connection.The local connection may be established by the native networkapplication 142, 152 operating on the mobile device 140, 150.

The system 100 may detect any type of status information available fromthe multiple, different types of networked devices. For instance, thesystem 100 may detect current operating status or values (e.g., sensedvalues) related to operations performed by the multiple, different typesof networked devices.

The system 100 provides a standardized interface for managing themultiple, different types of networked devices (230). For example, thesystem 100 may display a standardized interface that consolidatesmanagement of the multiple, different types of networked devices in asingle display. In addition, the system 100 may display a standardizedinterface that provides a similar look and feel regardless of which typeof network device is being managed. The standardized interface mayinclude a standardized display of the detected status of the multiple,different types of networked devices and standardized control elementsthat enable similar types of control operations to be performed on themultiple, different types of networked devices.

FIG. 3 illustrates an example of a standardized network devicemanagement interface 310. The network device management interface 310provides a standardized display of status information for severaldifferent types of network devices and includes standardized controlelements for managing the several different types of network devices.The network device management interface 310 may provide enhanced networkdevice management by providing a consolidated and easy to use interfacefor several different types of network devices.

The network device management interface 310 includes a useridentification portion 312 and a properties portion 314. The useridentification portion 312 indicates a user identifier for a user whosenetwork devices are currently being displayed in the network devicemanagement interface 310. The properties portion 314 displays a listingof properties (e.g., a home property, a vacation property, and an officeproperty) associated with the user identified in the user identificationportion 312. The listing of properties may include the propertiesmonitored by a monitoring system associated with the applicationdisplaying the network device management interface 310. A user mayselect one of the properties listed in the properties portion 314 tocause display of the network devices located at the selected property.Also, the properties portion 314 includes an “All” control that, whenselected, causes display of all of the network devices located at all ofthe properties. In this example, the “Home” property has been selectedand network devices located at the “Home” property are being displayed.

Based on selection of the “Home” property, the network device managementinterface 310 includes a security network devices portion 320, anappliances portion 330, and a computer network portion 340. The securitynetwork devices portion 320 displays network devices associated with the“Home” property that are part of a security system located at the “Home”property. As shown, the security network devices portion 320 has asensor portion 322 for a sensor included in the security system, acamera portion 324 for a camera included in the security system, and apanel portion 326 for a control panel included in the security system.

The appliances portion 330 displays network devices associated withappliances located at the “Home” property. As shown, the appliancesportion 330 has a refrigerator portion 332 for a refrigerator located atthe “Home” property, a light portion 334 for a lighting device locatedat the “Home” property, and a thermostat portion 336 for a thermostatlocated at the “Home” property.

The computer network portion 340 displays network devices associatedwith a computer network located at the “Home” property. As shown, thecomputer network portion 340 has a router portion 342 for a routerincluded in the computer network located at the “Home” property and aprinter portion 344 for a printer included in the computer networklocated at the “Home” property.

The sensor portion 322, the camera portion 324, the panel portion 326,the refrigerator portion 332, the lighting portion 334, the thermostatportion 336, the router portion 342, and the printer portion 344 allinclude a standardized set of status information and controls thatenable management of the network devices. For example, as shown, thestandardized set of status information includes a display of a currentstatus for the corresponding device (e.g., a current operating state orvalue of the corresponding device), a network identifier for thecorresponding device, and a communication protocol for the correspondingdevice. In addition, the controls that enable management of the networkdevices include a diagnose control that initiates a diagnosis routinefor the corresponding device when selected, a configure control thatinitiates a configuration process for the corresponding device whenselected, a statistics control that causes display of statistics trackedfor the corresponding device, and a remove control that causes removalof the corresponding device from the network of devices at the “Home”property.

The network device management interface 310 may provide enhanced networkdevice management because several different types of network devicesthat use several different types of communication protocols aredisplayed and managed in a consolidated and standardized interface. Inthis regard, the network device management interface 310 may provide asingle convenient place for user management of network devices that arelocated at a single property (or multiple properties) of the user. Inaddition, the network device management interface 310 provides adetailed visual interface with the same look and feel for managingseveral, different types of network devices, which may enhance a user'sconvenience in handling device management for several types of networkdevices that each have a limited or no display interface for devicecontrol.

Further, the network device management interface 310 includes an adddevice control 350, a generate report control 360, an automatic updatecontrol 370, and a cancel control 380. The add device control 350, whenactivated, initiates a process to add a new device to the network ofdevices at the “Home” property. For example, the add device control 350may cause display of another interface that enables a user to adddetails for a new device being added to the network of devices at the“Home” property. In this example, the add device control 350 may causedisplay of an add device wizard that poses a series of questions (e.g.,type of device, protocol used, etc.) to a user to gain the informationneeded to add the new device to the network of devices at the “Home”property.

The generate report control 360, when activated, initiates a process togenerate a report for the network of devices at the “Home” property. Thereport may be displayed or transmitted to another device after beinggenerated and may include status information tracked for the network ofdevices at the “Home” property over time. The status information mayinclude network device management commands associated with the networkdevices and operating status values for the network devices. Ingenerating the report, the network management application may aggregatestatus information tracked for each of the network devices at the “Home”property over time and combines the aggregated status information in areport. The report may include statistics computed based on theaggregated status information and charts or graphs that reflect theaggregated status information. The generate report control 360 mayprovide enhanced reporting capability because it provides a singlereport that includes information for all of the different, types ofnetwork devices located at the “Home” property.

The automatic update control 370, when activated, initiates a process toautomatically update the network of devices at the “Home” property. Forinstance, the automatic update control 370 may automatically cause anupdate to the network device management interface 310 by refreshingstatus information displayed by the network device management interface310.

The automatic update control 370 also may initiate a process thatautomatically searches for network devices located at the “Home”property and updates the network device management interface 310accordingly. For example, when a mobile device operating the networkmanagement application that is displaying the network device managementinterface 310 is located in the “Home” property, the network managementapplication automatically searches for devices using the wirelessprotocols supported by the network management application. When thenetwork management application detects a new device, the networkmanagement application may automatically add the new device to thenetwork of devices at the “Home” property and update the network devicemanagement interface 310 to reflect the addition. When the networkmanagement application fails to detect a device previously identified asbeing included in the network of devices at the “Home” property, thenetwork management application may automatically remove the undetecteddevice from the network of devices at the “Home” property and update thenetwork device management interface 310 to reflect the removal.

The cancel control 380, when activated, causes the network managementapplication to close the network device management interface 310 andcauses the device operating the network management application to resumenormal operation.

FIG. 4 illustrates an example process 400 for diagnosing a detectedproblem with a networked device. For convenience, a monitoring system(e.g., the monitoring application server 160), a native networkapplication loaded on a mobile device (e.g., the native networkapplication 142, 152 loaded on the mobile device 140, 150), and anetworked device (e.g., one of the devices 170, 172, 174, and 176) arereferenced as performing the process 400. However, similar methodologiesmay be applied in other implementations where different components areused to define the structure of the system, or where the functionalityis distributed differently among the components.

The monitoring system detects a problem with a networked device locatedat a property (402). For instance, the monitoring system may detect thatthe networked detect is experiencing an error in communication based ona lack of receipt of communications from the networked device. Themonitoring system may detect that the networked device is experiencinganother type of error based on an error code received from the networkeddevice or an observed lack of performance by networked device. Forexample, when the networked device communicates with a thermostat, themonitoring system may detect an error in controlling the thermostatbased on a control error code being provided by the networked device tothe monitoring system or based on a temperature measurement generated bythe thermostat not matching a thermostat temperature setting set by themonitoring system.

The monitoring system identifies data needed to diagnose the detectedproblem (404) and, in response, sends an alert with the identified datato a native mobile device network application loaded on a mobile device(406). The identified data may include a device identifier for thenetworked device for which the problem was detected, a problemidentifier that identifies the type of problem detected, and/orauthorization data (e.g., a security key) that authorizes another deviceto control the networked device. The device identifier may enable thenative mobile device network application to determine which networkeddevice needs diagnosis, the problem identifier may enable the nativemobile device network application to determine the type of problem thatneeds diagnosis, and the authorization data may enable the native mobiledevice network application at least temporary authorization tocommunicate with and control the networked device over a localconnection.

In some examples, the monitoring system may determine that the nativemobile device network application has been associated with the networkeddevice and is available to manage the networked device over a localconnection (e.g., a local wired connection or over a short rangewireless communication protocol, such as Z-Wave, ZigBee, Bluetooth,etc.). In response to this determination, the monitoring system sendsthe alert and the identified data to the native mobile device networkapplication to enable the native mobile device network application todiagnose the networked device.

The native mobile device network application receives the alert and theidentified data (408) and, in response to receiving the alert and theidentified data, displays the alert with diagnosis instructions (410).For instance, the alert and diagnosis instructions may includeinformation identifying the networked device that needs diagnosis andthe type of problem detected.

The diagnosis instructions also may include instructions for how a userestablishes a local connection with the networked device using thenative mobile device network application. For instance, the diagnosisinstructions may provide instructions for establishing a wiredconnection between the networked device and the mobile device operatingthe native mobile device network application. The diagnosis instructionsalso may provide instructions for establishing a wireless connectionbetween the networked device and the mobile device operating the nativemobile device network application (e.g., move within a certain distanceof the networked device and initiate a connection). The diagnosisinstructions further may provide instructions for authorizing the mobiledevice operating the native mobile device network application with thenetworked device (e.g., enter a particular pass code sequence withinlocal connection range of the networked device).

The native mobile device network application detects potential tointeract with the networked device (412). For example, the native mobiledevice network application may detect potential to interact with thenetworked device based on detecting a wired connection being establishedwith another device or determining that the mobile device is withinrange to wirelessly communicate with the networked device. In thisexample, the native mobile device network application may determine thatthe mobile device is within range to wirelessly communicate with thenetworked device based on a pinging communication exchanged with thenetworked device or by determining, based on a detected geographiclocation of the mobile device, that the mobile device is within athreshold distance of the networked device.

In response to detecting potential to interact with the networkeddevice, the native mobile device network application starts a diagnosisapplication for the detected problem (414). The native mobile devicenetwork application may select the diagnosis application from amongmultiple, possible diagnosis applications based on the networked deviceand/or the detected problem. For example, the native mobile devicenetwork application may select a diagnosis application that isappropriate for the communication protocol used by the networked device,the features included in the networked device, and the problem detected.The native mobile device network application also may start a genericdiagnosis application, but configure the generic diagnosis applicationbased on the networked device and/or the detected problem. The nativemobile device network application may start the diagnosis applicationautomatically, without human intervention, in response to detectingpotential to interact with the networked device, or may display asuggestion to start the diagnosis application in response to detectingpotential to interact with the networked device and await user inputconfirming the suggestion prior to starting the diagnosis application.

The native mobile device network application establishes a connectionwith the networked device (416). For instance, the native mobile devicenetwork application establishes a local connection with the networkeddevice. The local connection may be a local wired connection or a shortrange wireless connection that is enabled by a prior registration orpairing process between the native mobile device network application andthe networked device. The native mobile device network application mayuse authorization information (e.g., a security key) received from themonitoring system to authenticate itself to the networked device andgain authorization for establishing the connection.

After establishing the connection, the native mobile device networkapplication performs diagnosis operations using the establishedconnection (418) and sends an update to the monitoring system based onthe diagnosis operations (420). For instance, the native mobile devicenetwork application exchanges communications over the establishedconnection to attempt to diagnose the error experienced by the networkeddevice. The diagnosis operations may be selected by the native mobiledevice network application as diagnosis operations tailored to theproblem detected by the monitoring system. The update sent to themonitoring system may indicate that the error has been resolved based onthe diagnosis operations, may indicate that the error was not resolvedbased on the diagnosis operations, or may indicate more detailedinformation related to the error detected by the monitoring system.

The monitoring system receives the update (422) and handles thenetworked device accordingly (424). For example, when the updateindicates that the error has been resolved, the monitoring systemconfirms that the error has been resolved and resumes operation of thenetworked device. In another example, when the update indicates that theerror has not been resolved, the monitoring system maintains thenetworked device in a disabled state and takes action to causereplacement of the networked device (e.g., dispatches service personnelto the property at which the networked device is located or provides amessage suggesting replacement to a user associated with the networkeddevice). In a further example, when the update indicates more detaileddiagnosis information, the monitoring system analyzes the more detaileddiagnosis information and takes an appropriate action based on theanalysis (e.g., determines that the problem is being caused by themonitoring system and attempts to resolve the problem).

FIGS. 5A and 5B illustrate an example of diagnosing a detected problemwith a networked device. As shown, a property 510 includes a Z-Wavedevice 520. The Z-Wave device 520 may be a controllable unit connectedto or integrated in a lighting device, an entertainment device, ahousehold appliance, or a security system component. The Z-Wave device520 is managed by a mobile device 530 that has loaded a native mobiledevice network application. The native mobile device network applicationmay be used to transform the mobile device 530 into a Z-Wave controllerthat is able to interact with and control the Z-Wave device 520 usingthe Z-Wave communication protocol. The mobile device 530 may use thenative mobile device network application to provide a visual controldisplay for the Z-Wave device 520, which otherwise does not have acontrol interface or display.

A monitoring server 540 communicates with the Z-Wave device 520 and themobile device 530 over a network 550, which may be similar to thenetwork 105 described above with respect to FIG. 1. The monitoringserver 540 may exchange communications over the network 550 to receivedata generated by the Z-Wave device 520 or provide controlcommunications that ultimately reach the Z-Wave device 520. Theexchanged communication are not over the Z-Wave communication protocolbecause the monitoring server 540 is located remote from the property510 and, as such, is not physically close enough to the Z-Wave device520 to enable communication over the Z-Wave communication protocol. Assuch, the monitoring server 540 may exchange communications directlyover the network 550 with the Z-Wave device 520 when the Z-Wave device520 has another communication interface that enables communication overthe network 550. Alternatively, the monitoring server 540 may exchangecommunications indirectly with the Z-Wave device 520 when the Z-Wavedevice 520 does not have a communication interface that enablescommunication over the network 550, but is in communication with anotherdevice (e.g., a control panel) that is able to communicate over thenetwork 550.

In the example shown in FIG. 5A, the monitoring server 540 has detecteda problem with the Z-Wave device 520. Specifically, the monitoringserver 540 has detected the Z-Wave device 520 as being offline becausethe monitoring server 540 is not receiving communications from theZ-Wave device 520. In response to detecting the problem, the monitoringserver 540 identifies the mobile device 530 as being permitted tocontrol the Z-Wave device 520, determines to send an alert to the mobiledevice 530 to indicate the problem, and identifies a temporary key thatgives the mobile device 530 temporary access to control the Z-Wavedevice 520. The temporary key may be a temporary security key that theZ-Wave device 520 and the monitoring server 540 pre-set to enable themonitoring server 540 to authorize another device to access the Z-Wavedevice 520 using the Z-Wave communication protocol. The temporary keymay provide enhanced security for the Z-Wave device 520 because otherdevices will not be able to control the Z-Wave device 520 withoutauthorization from the monitoring server 540.

After identifying the temporary key, the monitoring server 540 sends, tothe mobile device 530, the temporary key with an alert that describesthe problem with the Z-Wave device 520 detected by the monitoring server540. The mobile device 530 receives the temporary key with the alertand, in response, displays an alert to indicate that an error with theZ-Wave device 520 has been detected. The mobile device 530 alsodetermines that it is presently too far away from the Z-Wave device 520to communicate with it over the Z-Wave communication protocol and, assuch, displays an instruction to go within range (e.g., three feet) ofthe Z-Wave device 520, so that the mobile device 530 can communicatewith the Z-Wave device 520 over the Z-Wave communication protocol.

In the example shown in FIG. 5B, a user has moved the mobile device 530within range (e.g., three feet) of the Z-Wave device 520. Accordingly,the mobile device 530 detects that it is within range of the Z-Wavedevice 520 and automatically, without human intervention, beginsattempting to communicate with the Z-Wave device 520 in an effort todiagnose the problem detected by the monitoring server 540.Specifically, the mobile device 530 automatically initiates a diagnosticroutine that is specifically directed to troubleshooting and resolvingthe remote communication error detected by the monitoring server 540. Inthis regard, the mobile device 530 may provide a user with an enhancedmechanism for controlling and diagnosing problems with the Z-Wave device520. Because the mobile device 530 is a device (e.g., a smart phone)that a user typically has in his or her possession for reasons otherthan controlling the Z-Wave device 520, the user may be quickly alertedto the detected problem and may be able to easily diagnose and remedythe problem without having locate or purchase other equipment (e.g., adedicated Z-Wave controller) to manage with the Z-Wave device 520.

FIG. 6 illustrates an example process 600 for updating firmware ofnetworked devices. For convenience, a monitoring system (e.g., themonitoring application server 160), a native network application loadedon a mobile device (e.g., the native network application 142, 152 loadedon the mobile device 140, 150), and a networked device (e.g., one of thedevices 170, 172, 174, and 176) are referenced as performing the process600. However, similar methodologies may be applied in otherimplementations where different components are used to define thestructure of the system, or where the functionality is distributeddifferently among the components.

The monitoring system detects new firmware for a networked devicelocated at a property (602). For instance, the monitoring system maydetect that a firmware update (e.g., a firmware patch) or an entirelynew firmware application has been stored in electronic storage of themonitoring system. The monitoring system may detect the new firmware inelectronic storage based on user input indicating that the firmware isfor the networked device.

The monitoring system identifies an ability to send the new firmware toa native mobile device network application loaded on a mobile device(604) and, in response, sends, over a network, the new firmware to thenative mobile device network application loaded on the mobile device(606). For instance, the monitoring system may determine that the nativemobile device network application has been associated with the networkeddevice and is available to transmit data to the networked device over alocal connection (e.g., a local wired connection or over a short rangewireless communication protocol, such as Z-Wave, ZigBee, Bluetooth,etc.). The monitoring system sends the new firmware to the native mobiledevice network application over a network connection (e.g., theInternet). The network connection may be less time-consuming or lessexpensive than other communication options (if any) the monitoringsystem has for communicating with the networked device.

The native mobile device network application receives the new firmware(608) and, in response to receiving the new firmware, establishes aconnection with the networked device (610). For instance, the nativemobile device network application establishes a local connection withthe networked device. The local connection may be a local wiredconnection or a short range wireless connection that is enabled by aprior registration or pairing process between the native mobile devicenetwork application and the networked device. The native mobile devicenetwork application may display an indication that new firmware has beenreceived for the networked device with a request that the user establisha local connection with the networked device to enable a firmwareupdate. The request may be a request to establish a wired connectionbetween the networked device and the mobile device or a request to movethe mobile device to location that is within range of the networkeddevice for a short range wireless communication protocol (e.g., movewithin three feet of the device). The native mobile device networkapplication also may monitor its ability to communicate with thenetworked device over a short range wireless communication protocol andautomatically, without human intervention, establish the connection whenthe native mobile device network application detects ability tocommunicate with the networked device over the short range wirelesscommunication protocol.

After establishing the connection, the native mobile device networkapplication transmits the new firmware over the established connection(612) and the networked device receives the new firmware (614). Thenetworked device then updates its firmware using the new firmwarereceived from the native mobile device network application over theestablished connection (616).

FIG. 7 illustrates an example of updating firmware of a networkeddevice. As shown, a property 710 is monitored by a local monitoringsystem (e.g., a security system) located at the property 710. The localmonitoring system includes a control panel 720 and a camera 725. Thecontrol panel 720 displays status information for the local monitoringsystem and includes one or more input controls that enable control ofthe local monitoring system. The camera 725 captures images of theproperty 710, which may be used to detect security events and enableremote visual monitoring of the property 710. The local monitoringsystem has been described as including only the control panel 720 andthe camera 725 for brevity, but may include many more sensors andfeatures.

The devices of the local monitoring system (e.g., the control panel 720and the camera 725) are managed by a mobile device 730 that has loaded anative mobile device network application. The mobile device 730 may usethe native mobile device network application for inclusion or removal ofdevices from the local monitoring system, monitoring status of devicesfrom the local monitoring system, diagnosing problems with devices fromthe local monitoring system, configuring attributes of devices from thelocal monitoring system, exchanging data (e.g., firmware updates) withdevices from the local monitoring system, or performing any othertechniques described throughout this disclosure as being performed by anative mobile device network application. The mobile device 730 may usethe native mobile device network application to provide an enhancedvisual control display for the control panel 720 and the camera 725 whenthe control panel 720 and the camera 725 have a limited or no displaydevice.

A monitoring server 740 communicates with the control panel 720 and themobile device 730 over a network 750, which may be similar to thenetwork 105 described above with respect to FIG. 1. More specifically,the monitoring server 740 communicates, over a cellular (e.g., GSM)portion of the network 750, with a network communications moduleincluded in the control panel 720 and communicates, over an IP-based(e.g., the Internet) portion of the network 750, with the mobile device730. The monitoring server 740 receives monitoring system data (e.g.,detected security alerts) from the control panel 720 and, in someexamples, receives image data captured by the camera 725 through thecontrol panel 720. The monitoring server 740 exchanges, with the mobiledevice 730, data related to management of devices included in the localmonitoring system. In this example, it may be more expensive and/ortime-consuming for the monitoring server 740 to communicate with thecontrol panel 720 over the cellular (e.g., GSM) portion of the network750, than for the monitoring server 740 to communicate with the mobiledevice 730 over the IP-based (e.g., the Internet) portion of the network750.

Because of the differences in the monitoring server's 740 ability tocommunicate with the control panel 720 and the camera 725 as compared tothe mobile device 730, the monitoring server 740 uses the mobile device730 as conduit for transmitting larger data, such as firmware updates,to the control panel 720 and the camera 725. In this example, themonitoring server 740 detects that new firmware is available for thecontrol panel 720 and the camera 725 and, in response to detecting thenew firmware, determines how best to transmit the new firmware to thecontrol panel 720 and the camera 725. Specifically, the monitoringserver 740 determines that the control panel 720 and the camera 725 areonly able to receive data from the monitoring server 740 over thecellular (e.g., GSM) portion of the network 750 and also determines thatthe mobile device 730 has loaded the native mobile device networkapplication and is available to assist in managing firmware updates forthe control panel 720 and the camera 725. Based on these determinations,the monitoring server 740 transmits the new firmware for the controlpanel 720 and the camera 725 to the mobile device 730 over the IP-based(e.g., the Internet) portion of the network 750.

After receiving the new firmware for the control panel 720 and thecamera 725, the mobile device 730 monitors for a time when the mobiledevice 730 is able to establish a local connection with the controlpanel 720 and the camera 725. The local connection may be a wiredconnection or a short range wireless connection, either of which may befaster and/or less expensive than the monitoring server 740communicating with the control panel 720 over the cellular (e.g., GSM)portion of the network 750. When the mobile device 730 detects abilityto establish a local connection with the control panel 720 and/or thecamera 725, the mobile device 730 transmits the new firmware for thecontrol panel 720 and/or the camera 725 to the control panel 720 and/orthe camera 725 over the established local connection. In this regard,the mobile device 730 acts as a conduit for providing the new firmwareto the control panel 720 and the camera 725, which may result in anefficient firmware update for the control panel 720 and the camera 725that does not involve direct communication by the control panel 720 orthe camera 725 with the monitoring server 740.

In some implementations, the monitoring server 740 may intelligentlydetermine when to use the mobile device 730 as a conduit for exchangingdata (e.g., firmware updates) between itself and the control panel 720and the camera 725. In these implementations, when the camera 725 is anIP-based camera that is able to communicate with the monitoring server740 over the IP-based (e.g., the Internet) portion of the network 750,the monitoring server 740 may directly transmit data (e.g., firmwareupdates) to the camera 725 and indirectly transmit data (e.g., firmwareupdates) to the control panel 720 through the mobile device 730. Themonitoring server 740 also may consider the size of the data that needsto be exchanged and the speed in which the transfer is needed whendeciding how the transfer should be completed. For example, when thedata is relatively small, the monitoring server 740 may directlyexchange the data with the control panel 720, rather than going throughthe mobile device 730. In another example, when the data is critical(e.g., a critical firmware update) and the mobile device 730 is detectedas being remote from the control panel 720 and the camera 725, themonitoring server 740 may directly exchange the critical data (e.g., thecritical firmware update) with the control panel 720 because theexchange is of high importance and the mobile device 730 is unlikely tobe able to relay the critical data to the control panel 720 and thecamera 725 in a timely manner due to its remote location from thecontrol panel 720 and the camera 725.

The described systems, methods, and techniques may be implemented indigital electronic circuitry, computer hardware, firmware, software, orin combinations of these elements. Apparatus implementing thesetechniques may include appropriate input and output devices, a computerprocessor, and a computer program product tangibly embodied in amachine-readable storage device for execution by a programmableprocessor. A process implementing these techniques may be performed by aprogrammable processor executing a program of instructions to performdesired functions by operating on input data and generating appropriateoutput. The techniques may be implemented in one or more computerprograms that are executable on a programmable system including at leastone programmable processor coupled to receive data and instructionsfrom, and to transmit data and instructions to, a data storage system,at least one input device, and at least one output device. Each computerprogram may be implemented in a high-level procedural or object-orientedprogramming language, or in assembly or machine language if desired; andin any case, the language may be a compiled or interpreted language.Suitable processors include, by way of example, both general and specialpurpose microprocessors. Generally, a processor will receiveinstructions and data from a read-only memory and/or a random accessmemory. Storage devices suitable for tangibly embodying computer programinstructions and data include all forms of non-volatile memory,including by way of example semiconductor memory devices, such asErasable Programmable Read-Only Memory (EPROM), Electrically ErasableProgrammable Read-Only Memory (EEPROM), and flash memory devices;magnetic disks such as internal hard disks and removable disks;magneto-optical disks; and Compact Disc Read-Only Memory (CD-ROM). Anyof the foregoing may be supplemented by, or incorporated in,specially-designed ASICs (application-specific integrated circuits).

It will be understood that various modifications may be made. Forexample, other useful implementations could be achieved if steps of thedisclosed techniques were performed in a different order and/or ifcomponents in the disclosed systems were combined in a different mannerand/or replaced or supplemented by other components. Accordingly, otherimplementations are within the scope of the disclosure.

What is claimed is:
 1. A system for monitoring local network deviceslocated at a property, the system comprising: a monitoring system thatis configured to monitor a client's local network, comprising locallynetworked devices that are located at the client's property; a nativemobile device network application loaded onto a mobile device, thenative mobile device network application including instructions that,when executed by the mobile device, cause the mobile device to performoperations comprising: tracking the locally networked devices that arelocated at the property; based on the tracking of the locally networkeddevices that are located at the property, detecting status of thelocally networked devices that are located at the property; andproviding an interface for managing the locally networked deviceslocated at the property, wherein the monitoring system is configured toperform operations comprising: detecting a problem with one of thelocally networked devices, and in response to detecting the problem,sending an alert to the native mobile device network applicationidentifying the detected problem and the locally networked deviceassociated with the detected problem; and wherein the native mobiledevice network application further includes instructions that, whenexecuted by the mobile device, cause the mobile device to performoperations comprising: receiving the alert identifying the detectedproblem and the locally networked device associated with the detectedproblem; in response to receiving the alert, determining that the mobiledevice is unable to communicate with the locally networked deviceassociated with the detected problem; based on the determination thatthe mobile device is unable to communicate with the locally networkeddevice associated with the detected problem, outputting, on a display ofthe mobile device, alert information for the detected problem, the alertinformation including a description of the detected problem and adescription of how to diagnose the detected problem using a localconnection between the mobile device and the locally networked deviceassociated with the detected problem; after outputting the alertinformation, detecting potential to establish the local connectionbetween the mobile device and the locally networked device associatedwith the detected problem; and in response to detecting potential toestablish the local connection between the mobile device and the locallynetworked device associated with the detected problem, establishing thelocal connection between the mobile device and the locally networkeddevice associated with the detected problem and starting a diagnosisprocess used to diagnose the detected problem using the localconnection, the mobile device and the locally networked device bothbeing located within the property to establish the local connection as adirect connection between the mobile device and the locally networkeddevice, wherein starting the diagnosis process used to diagnose thedetected problem comprises: selecting a diagnosis application that isappropriate for a communication protocol used by the locally networkeddevice associated with the detected problem, features included in thelocally networked device associated with the detected problem, and theproblem detected; and starting the diagnosis application automatically,without human intervention, in response to detecting potential tointeract with the locally networked device associated with the detectedproblem.
 2. The system of claim 1: wherein outputting alert informationfor the detected problem comprises outputting alert information thatincludes a description of how to establish the local connection with thelocally networked device associated with the detected problem using thenative mobile device network application; wherein detecting potential toestablish the local connection between the mobile device and the locallynetworked device associated with the detected problem comprisesdetecting establishment of the local connection with the locallynetworked device associated with the detected problem using the nativemobile device network application; and wherein starting the diagnosisprocess used to diagnose the detected problem comprises using the localconnection to diagnose the detected problem.
 3. The system of claim 1:wherein outputting alert information for the detected problem comprisesoutputting alert information that includes a description of how toestablish a wired connection between the locally networked deviceassociated with the detected problem and the mobile device; whereindetecting potential to establish the local connection between the mobiledevice and the locally networked device associated with the detectedproblem comprises detecting establishment of the wired connection withthe locally networked device associated with the detected problem usingthe native mobile device network application; and wherein starting thediagnosis process used to diagnose the detected problem comprises usingthe wired connection to diagnose the detected problem.
 4. The system ofclaim 1: wherein outputting alert information for the detected problemcomprises outputting alert information that includes a description ofhow to establish a short-range wireless connection between the locallynetworked device associated with the detected problem and the mobiledevice; wherein detecting potential to establish the local connectionbetween the mobile device and the locally networked device associatedwith the detected problem comprises detecting establishment of theshort-range wireless connection with the locally networked deviceassociated with the detected problem using the native mobile devicenetwork application; and wherein starting the diagnosis process used todiagnose the detected problem comprises using the short-range wirelessconnection to diagnose the detected problem.
 5. The system of claim 4,wherein outputting alert information that includes a description of howto establish a short-range wireless connection between the locallynetworked device associated with the detected problem and the mobiledevice comprises outputting alert information that instructs a user ofthe mobile device to move within a certain distance of the locallynetworked device associated with the detected problem.
 6. The system ofclaim 1: wherein outputting alert information for the detected problemcomprises outputting alert information that includes a description ofhow to authorize the mobile device with the locally networked deviceassociated with the detected problem; wherein detecting potential toestablish the local connection between the mobile device and the locallynetworked device associated with the detected problem comprisesdetecting establishment of an authorized connection with the locallynetworked device associated with the detected problem using the nativemobile device network application; and wherein starting the diagnosisprocess used to diagnose the detected problem comprises using theauthorized connection to diagnose the detected problem.
 7. The system ofclaim 1, wherein starting the diagnosis process used to diagnose thedetected problem comprises: selecting a diagnosis application that isappropriate for a communication protocol used by the locally networkeddevice associated with the detected problem, features included in thelocally networked device associated with the detected problem, and theproblem detected; outputting a suggestion to start the diagnosisapplication in response to detecting potential to interact with thelocally networked device; and awaiting user input confirming thesuggestion prior to starting the diagnosis application.
 8. The system ofclaim 1, wherein starting the diagnosis process used to diagnose thedetected problem comprises automatically, without human intervention,starting a diagnosis process used to diagnose the detected problem. 9.The system of claim 1: wherein the native mobile device networkapplication further includes instructions that, when executed by themobile device, cause the mobile device to perform operations comprisingsending an update to the monitoring system that describes results of theperformance of the diagnosis operations; and wherein the monitoringsystem is further configured to perform operations comprising: receivingthe update that describes results of the performance of the diagnosisoperations, and handling the locally networked device associated withthe detected problem based on the received update that describes resultsof the performance of the diagnosis operations.
 10. The method of claim1: wherein the alert sent to the native mobile device networkapplication is a result of managing multiple alerts from within thelocal network comprised of locally networked devices; wherein themanaging of multiple alerts is performed by an entity of the mobiledevice network application able to dynamically associate combinations ofalerts to a root cause; wherein the root cause is then sent to thenative mobile device network application as the alert.
 11. The method ofclaim 1: wherein outputting alert information for the detected problemcomprises outputting alert information that includes a description ofhow to deauthorize one of the locally networked devices associated withthe detected problem; wherein detecting potential to establish the localconnection between the mobile device and the locally networked deviceassociated with the detected problem comprises detecting establishmentof an authorized connection with the locally networked device associatedwith the detected problem using the native mobile device networkapplication; and wherein starting the diagnosis process used to diagnosethe detected problem comprises using the authorized connection todiagnose the detected problem.
 12. A method comprising: tracking locallynetworked devices that are located at a property, the property beingmonitored by a monitoring system and the tracking being performed by anative mobile device network application loaded onto a mobile device;based on the tracking of the locally networked devices that are locatedat the property, detecting status of the locally networked devices thatare located at the property; providing an interface for managing thelocally networked devices located at the property; detecting a problemwith one of the locally networked devices; in response to detecting theproblem, sending an alert to the native mobile device networkapplication identifying the detected problem and the locally networkeddevice associated with the detected problem; receiving, by the nativemobile device network application, the alert identifying the detectedproblem and the locally networked device associated with the detectedproblem; in response to receiving the alert, determining that the mobiledevice is unable to communicate with the locally networked deviceassociated with the detected problem; based on the determination thatthe mobile device is unable to communicate with the locally networkeddevice associated with the detected problem, outputting, on a display ofthe mobile device, alert information for the detected problem, the alertinformation including a description of the detected problem and adescription of how to diagnose the detected problem using a localconnection between the mobile device and the locally networked deviceassociated with the detected problem; after outputting the alertinformation, detecting potential to establish the local connectionbetween the mobile device and the locally networked device associatedwith the detected problem; and in response to detecting potential toestablish the local connection between the mobile device and the locallynetworked device associated with the detected problem, establishing thelocal connection between the mobile device and the locally networkeddevice associated with the detected problem and starting a diagnosisprocess used to diagnose the detected problem using the localconnection, the mobile device and the locally networked device bothbeing located within the property to establish the local connection as adirect connection between the mobile device and the locally networkeddevice, wherein starting the diagnosis process used to diagnose thedetected problem comprises: selecting a diagnosis application that isappropriate for a communication protocol used by the locally networkeddevice associated with the detected problem, features included in thelocally networked device associated with the detected problem, and theproblem detected; and starting the diagnosis application automatically,without human intervention, in response to detecting potential tointeract with the locally networked device associated with the detectedproblem.
 13. The method of claim 12: wherein outputting alertinformation for the detected problem comprises outputting alertinformation that includes a description of how to establish the localconnection with the locally networked device associated with thedetected problem using the native mobile device network application;wherein detecting potential to establish the local connection betweenthe mobile device and the locally networked device associated with thedetected problem comprises detecting establishment of the localconnection with the locally networked device associated with thedetected problem using the native mobile device network application; andwherein starting the diagnosis process used to diagnose the detectedproblem comprises using the local connection to diagnose the detectedproblem.
 14. The method of claim 12: wherein outputting alertinformation for the detected problem comprises outputting alertinformation that includes a description of how to establish a wiredconnection between the locally networked device associated with thedetected problem and the mobile device; wherein detecting potential toestablish the local connection between the mobile device and the locallynetworked device associated with the detected problem comprisesdetecting establishment of the wired connection with the locallynetworked device associated with the detected problem using the nativemobile device network application; and wherein starting the diagnosisprocess used to diagnose the detected problem comprises using the wiredconnection to diagnose the detected problem.
 15. The method of claim 12:wherein outputting alert information for the detected problem comprisesoutputting alert information that includes a description of how toestablish a short-range wireless connection between the locallynetworked device associated with the detected problem and the mobiledevice; wherein detecting potential to establish the local connectionbetween the mobile device and the locally networked device associatedwith the detected problem comprises detecting establishment of theshort-range wireless connection with the locally networked deviceassociated with the detected problem using the native mobile devicenetwork application; and wherein starting the diagnosis process used todiagnose the detected problem comprises using the short-range wirelessconnection to diagnose the detected problem.
 16. The method of claim 15,wherein outputting alert information that includes a description of howto establish a short-range wireless connection between the locallynetworked device associated with the detected problem and the mobiledevice comprises outputting alert information that instructs a user ofthe mobile device to move within a certain distance of the locallynetworked device associated with the detected problem.
 17. The method ofclaim 12: wherein outputting alert information for the detected problemcomprises outputting alert information that includes a description ofhow to authorize the mobile device with the locally networked deviceassociated with the detected problem; wherein detecting potential toestablish the local connection between the mobile device and the locallynetworked device associated with the detected problem comprisesdetecting establishment of an authorized connection with the locallynetworked device associated with the detected problem using the nativemobile device network application; and wherein starting the diagnosisprocess used to diagnose the detected problem comprises using theauthorized connection to diagnose the detected problem.
 18. The methodof claim 12, wherein starting the diagnosis process used to diagnose thedetected problem comprises: selecting a diagnosis application that isappropriate for a communication protocol used by the locally networkeddevice associated with the detected problem, features included in thelocally networked device associated with the detected problem, and theproblem detected; outputting a suggestion to start the diagnosisapplication in response to detecting potential to interact with thelocally networked device; and awaiting user input confirming thesuggestion prior to starting the diagnosis application.
 19. The methodof claim 12, wherein starting the diagnosis process used to diagnose thedetected problem comprises automatically, without human intervention,starting a diagnosis process used to diagnose the detected problem. 20.The method of claim 12, further comprising: sending an update to themonitoring system that describes results of the performance of thediagnosis operations; receiving the update that describes results of theperformance of the diagnosis operations, and handling the locallynetworked device associated with the detected problem based on thereceived update that describes results of the performance of thediagnosis operations.
 21. The method of claim 12: wherein the alert sentto the native mobile device network application is a result of managingmultiple alerts from within the local network comprised of locallynetworked devices; wherein the managing of multiple alerts is performedby an entity of the mobile device network application able todynamically associate combinations of alerts to a root cause; whereinthe root cause is then sent to the native mobile device networkapplication as the alert.
 22. The method of claim 12: wherein outputtingalert information for the detected problem comprises outputting alertinformation that includes a description of how to deauthorize one of thelocally networked devices associated with the detected problem; whereindetecting potential to establish the local connection between the mobiledevice and the locally networked device associated with the detectedproblem comprises detecting establishment of an authorized connectionwith the locally networked device associated with the detected problemusing the native mobile device network application; and wherein startingthe diagnosis process used to diagnose the detected problem comprisesusing the authorized connection to diagnose the detected problem.